Fantom Bridge.

A Fantom Bridge locks or burns your asset on one chain and mints the matching amount on Fantom, so value crosses from Ethereum to Fantom without ever sitting in a custodian's account. Deposit and the bridge contract on Ethereum holds your ETH or token while Fantom credits your address once the source transaction is confirmed. Withdraw and the sequence reverses: the asset is burned on Fantom and released on Ethereum after the exit is proven. Because Fantom's own consensus finalizes blocks in about a second, the Fantom side of a transfer rarely becomes the slow part of the trip — the Ethereum confirmation usually sets the pace instead.

Why Lachesis speeds up the Fantom side

Fantom runs on Lachesis, an asynchronous Byzantine fault-tolerant consensus described in general BFT literature as a family of protocols that reach agreement without waiting on a single leader. Validators exchange event blocks and reach finality in roughly a second rather than waiting several minutes for probabilistic confirmations, which is why a deposit typically shows up on Fantom almost as soon as Ethereum has settled the source transaction.

What you can carry across

ETH and major stablecoins such as USDC and USDT are the common deposits, alongside most ERC-20 tokens Fantom's ecosystem lists. The asset keeps its identity once it lands — bridged USDC still spends as USDC on Fantom DeFi — and the same canonical path can send it back to Ethereum whenever you choose.

Fantom charges transaction fees in its native token, FTM, not in ETH, so the first thing to plan after a Fantom Bridge deposit is a small FTM balance for gas. Fantom's team has also been rolling the network forward into Sonic, an upgraded execution layer that keeps the same self-custody model while raising throughput; the native token on that upgraded chain is referred to as S. Either way, arriving with a little gas already set aside saves a second trip to a bridge just to cover a swap.

Getting your first FTM

Many people bridge a small amount of FTM alongside their main asset so the very first transaction on Fantom has gas ready. Others arrive with only ETH or a stablecoin and swap a portion for FTM on a Fantom-based exchange immediately after the deposit confirms — either approach works, as long as some FTM lands before you try to interact with anything else.

Checking the migration to Sonic

Because the network has been transitioning toward Sonic, it is worth confirming which chain a given app or bridge route currently targets before moving a large balance. The Fantom documentation tracks the current state of that migration and which contracts are considered canonical at any given time.

A Fantom Bridge deposit costs Ethereum gas for the source transaction plus a small protocol fee; once assets are on Fantom, further activity is paid in FTM and tends to be inexpensive thanks to the network's own fee market. Timing leans in your favor on both legs compared with many optimistic rollups, since Lachesis finality removes the long dispute window that those designs require before releasing funds. The table below lays out what to expect.

Direction	What you pay	Typical time
Deposit to Fantom	Ethereum gas + protocol fee	Minutes after confirmation
Activity on Fantom	FTM gas (low cost)	About a second per transaction
Withdrawal to Ethereum	Fantom gas, then Ethereum gas to finalize	Minutes to a short settlement period

Reading the quote before you sign

Every quote should show the amount leaving, the fee, and the amount that lands on the other side; judge a route by that landing figure rather than the advertised rate. You can verify a completed transfer independently by looking up your address on FTMScan, which records every deposit and withdrawal that touches the network.

The sequence stays the same each time you use it, which makes a Fantom Bridge predictable once you have completed it once.

• Pick Ethereum as the source chain and Fantom as the destination in your bridge of choice.
• Enter the amount and review the fee plus the amount that will arrive on Fantom.
• Approve the token if it is an ERC-20, then sign the deposit and pay Ethereum gas.
• Wait for Ethereum to confirm; the balance appears on Fantom within a few minutes.
• To go back, start a withdrawal from Fantom and claim the released asset on Ethereum once it settles.

A canonical Fantom Bridge never takes custody of what you send — your keys sign every step, and the contract only moves what you approve. The risks that remain are the ones you control at the moment of signing, so it pays to slow down there rather than anywhere else.

Managing token approvals

Grant an ERC-20 approval sized to the transfer you are actually making rather than an open-ended allowance, and clear out old approvals from bridges or apps you no longer use. A wallet with fewer standing permissions gives any future exploit less to reach for.

Recovery phrases stay offline

A legitimate Fantom Bridge interface only ever asks for a transaction signature it shows you in your own wallet. It has no reason to request your recovery words in a form, a chat window, or a support ticket, and any message that asks for them by any other channel should be ignored outright.

Bridging is only the arrival point. Once assets sit on Fantom, they work across its decentralized exchanges, lending markets and liquidity pools, with FTM covering the gas for every interaction. You can track the network's active liquidity and the apps holding it on DefiLlama's Fantom page before deciding where to put a deposit to work, and when you are ready to leave, the same canonical exit route hands native ETH back on Ethereum.

You can reach Fantom through the canonical Fantom Bridge or through a third-party liquidity bridge that fronts funds instead of waiting on the official contract. The canonical path mints the reference representation of your asset and suits larger or long-term transfers, while a third-party route can sometimes complete faster because it uses its own reserves rather than the standard settlement sequence — at the cost of an extra fee and a separate trust assumption. Background on how bridging works at a protocol level is covered in Ethereum's own developer documentation, which is useful context no matter which specific route you end up choosing.